Skip to main content

Error Response Format

All SuperDoc API errors follow a consistent JSON structure:
string
required
Machine-readable error code for programmatic handling
string
required
HTTP status text (e.g., “Bad Request”, “Unauthorized”)
string
required
Human-readable error description
string
required
Unique identifier for the request (useful for support)
string
ISO 8601 timestamp when the error occurred

HTTP Status Codes

SuperDoc API uses standard HTTP status codes:
Client Error - Invalid request format or parametersCommon causes:
  • Missing required parameters
  • Invalid file format
  • Malformed request body
  • File too large
Authentication Error - Invalid or missing API key Common causes: - Missing Authorization header - Invalid API key format - Expired or revoked API key
Authorization Error - Valid credentials but insufficient permissions Common causes: - Plan limitations exceeded - Feature not available in current plan - IP address restrictions
Rate Limiting - Request quota exceeded Common causes: - Hourly rate limit exceeded - Daily rate limit exceeded - Burst limit exceeded
Server Error - Unexpected server-side issue Common causes: - Temporary service disruption - Document processing failure - Resource exhaustion
Service Unavailable - Temporary service interruptionCommon causes:
  • Scheduled maintenance
  • System overload
  • Dependency failures

Common Error Codes

Authentication Errors

File Processing Errors

Rate Limiting Errors

Error Handling Strategies

Basic Error Handling

Advanced Error Handling with Retry Logic

Error Handling Best Practices

Handle different error types with appropriate responses:
Always log errors with context:
Translate technical errors into user-friendly messages:
Provide alternatives when the API is unavailable:

Monitoring and Alerting

Error Rate Monitoring

Track error rates to identify issues:

Health Check Implementation

Getting Help

When encountering persistent errors:

Check Status Page

Monitor service status and planned maintenance

Contact Support

Include the requestId for faster troubleshooting
Always include the requestId from error responses when contacting support. This helps us quickly locate and diagnose the specific request.